-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
encourage NixOS configuration, nix-shell and discourage nix-env #514
Conversation
9941b05
to
4e0e76f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change has been approved by the IANEO, the International Anti-nix-env Organization. Consider your work worthy. ✅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks alright.
Let's maybe move the "long description" above the installation instructions?
Ping @roberth
&:before { | ||
content: "$ " | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The point of having this in a :before
is that the dollar sign is not copied when you select the whole block
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pre-existing css is the strangest I've ever seen. What's up with all the nth-child
selectors? Positional as opposed to named css? That's just an awful idea.
So I can't blame Matthew for not restoring this functionality for nix-env. He had to remove the $
for the declarative installation methods, which are more important anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know, it's awful. There's no need to stick to that pattern though: adding a shell-commands
class outside the hierarchy would be fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not familiar with elm enough to accomplish this. If you could make a PR that does it to my fork, I'll merge it and it'll be done. But I think the scope of this PR will then have been increased more than it needs to be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No problem! I pushed to your branch directly.
An example with a shell file would be nice, but certainly no blocker. |
So that it's not selected when you select the whole code block
@ncfavier Having reviewed your changes, it looks great. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff :)
@garbas This looks ready to merge. |
This would close #508
High level changes
nix-env
now has a warning associated with it, which explains that it has side-effects which may require cleanup by the user manually after usage like a traditional package manager.environment.systemPackages
ornix-shell -p
.Internal changes
FromNixOS
andFromNixpkgs
withViaNixOS
,ViaNixShell
andViaNixEnv
$
before every instance of.terminal
infrontend/src/index.less
because I was not easily able to case split on imperative cmds likenix-shell -p
and the code for a NixOS configuration. Instead,$
has been placed manually into each text field where a command is imperative, such asnix build
for flakes andnix-shell
.div
function, and would appreciate someone to help with thatWhat it looks like
NixOS Configuration
nix-shell
nix-env